The test program I am running does a 100mm X move starting from 0:
F2000 G1 X-100 and the segment data is: "SegA",408.364844,0,0, 0.000000,0.000000,-165000.000000,0.000188,0.000000,0.000000, -50000.000000,0.000000,-165000.000000,0.000188,0.000000,0.000000 "SegB",0.000015,0,1,1.968504,1.312336,1.312336,10.000000,10.000000,inf,40000.000000,0.000000,3.000000,0.000000,0.000000 "Linear",0.000024,0,0, 0.000000,2.540000,0.000000,0.000000,0.131234"Linear",0.000029,0,1, 0.000000,0.000000,0.666667,0.043745,1.434383"SegA",0.102587,1,1, -50000.000000,0.000000,-165000.000000,0.000188,0.000000,0.000000, -100000.000000,0.000000,-165000.000000,0.000188,0.000000,0.000000 "SegB",0.102597,1,1,1.968504,1.312336,1.312336,10.000000,10.000000,inf,3149.606201,1.312336,3.000000,0.000000,0.000000 "Linear",0.102604,1,1, 0.000000,0.000000,0.666667,0.000000,1.434383"Linear",0.102792,1,2, 0.000000,-2.540000,0.666667,0.956255,0.131234SegA/B are data from the segment itself, and "Linear" is output for each trip state. I have highlighted the X coordinates and the 5 coefficients. Step units are in um. The velocity (0.6666 * 50000) is correct (2000mm/min = 33333 um/sec). The configured acceleration is 500,000 um/s^2, but the above b coefficients (2.54) when multiplied by 2 * 50000um gives 254,000 um/s^2. The digits 254 make me suspect an inch/mm conversion error, but if that was the case then the velocity would be way off. Anyway, this is a coding error or misunderstanding on my part, so don't worry about it. I'll keep looking. Regards, SJH
|
|